I can't push because Git operations on github are down at the moment. Will push tomorrow.

As for the tests @ulysses4ever, the current test-suite makes use of this both by the roundtrip of project configurations and by some tests that make use of local+noindex repos such as the ones added recently by @9999years. I consider that sufficient testing.

the current test-suite makes use of this both by the roundtrip of project configurations and by some tests that make use of local+noindex repos such as the ones added recently by @9999years. I consider that sufficient testing.

It's just that if anything in the current setup exercises this functionality, I expect the setup to need an update after these changes.

The previous PR that was merged did change the OutputNormalizer. It then worked with //./ paths. Now it works with file+noindex:C:/ paths.

One could argue that the right syntax would be:

file+noindex:///C:/foo

But that is not understood by network-uri. It is however what .NET does:

➜ [System.Uri]'C:/foo.txt'

AbsolutePath   : C:/foo.txt
AbsoluteUri    : file:///C:/foo.txt
...

In any case .NET also supports the syntax we use here so it should be fine:

➜ [System.Uri]'file:C:/foo.txt'

AbsolutePath   : C:/foo.txt
AbsoluteUri    : file:///C:/foo.txt
...

Probably the right thing to do would be to make use of file-uri for file+noindex paths, but that would require us to not first read it as a network-uri. The good news is that file-uri understands both versions and both are "the same" so once we make this change and recommend file:/// the previous code won't break:

ghci> parseFileURI ExtendedWindows  "file:///C:/foo.txt"
Right (FileURI {fileAuth = Nothing, filePath = "C:/foo.txt"})
ghci> parseFileURI ExtendedWindows  "file:C:/foo.txt"
Right (FileURI {fileAuth = Nothing, filePath = "C:/foo.txt"})

cc @hasufell